|
 (Disk 1).iso/pc/technical documentation/macintosh technotes and q&as/technotes/tn/tn1142/images/systemfile.gif)
|
Inside the System File
(Continued)
|
Translation Manager
The Translation Manager provides file and scrap
translation to allow data to be used by applications
other than those that originally created the data. The
following changes have been made in the Translation
Manager:
- The Translation Manager implementation has been moved
to the System file, and the user interface has been moved
from the now-obsolete Mac OS Easy Open control panel to
the File Exchange control panel's "File Translation"
panel.
- The Translation manager is now implemented in PowerPC
code.
- The available translator lists are now rebuilt
dynamically. If a translation extension component is
registered sometime after startup, the Translation
Manager will recognize it immediately.
- Contents of the "Translated Documents" folder are now
removed at system startup time. The Translation Manager
places automatically translated documents into this
folder before passing them on to applications.
- With both QuickTime and MacLinkPlus for Easy Open
installed, there are more than 64 possible translation
configurations for Desktop Translators, but Desktop
Translators could only be configured to use one of the
first 64 translations available. This limitation for
Desktop Translators has been removed.
- Applications which open files of a given type may do
so without translation. Prior to File Exchange 3.0, if an
application claimed (through its bundle and/or
'open' resource) that it could open files of
a given type, documents of that type with a different
creator type than the application's creator type would be
translated rather than opened directly. Now, such
documents are opened directly without translation. To see
an example of this behavior, under Mac OS 8.1 drop a
MoviePlayer movie onto SimpleText. It will open as a
picture rather than a movie (as it will be translated by
the QuickTime translator first). Now, the movie will open
as expected.
- Translation Manager no longer creates a temporary
heap zone for translation extension components. Instead,
translation extension components are loaded into the
system heap. This means that translation extensions are
no longer allowed to "leak" memory, as their calls to
NewPtr and NewHandle now
operate in the system heap. Contrary to what is stated in
Inside
Macintosh: More Macintosh Toolbox, the
Translation Manager now disposes of the translation
advertisement when tearing down the translation progress
dialog (since the translation advertisement is now
allocated in the system heap rather than a temporary
heap).
|
 (Disk 1).iso/pc/technical documentation/macintosh technotes and q&as/technotes/tn/tn1142/images/blueline.gif){kind=small}